Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixed broken Julia LSP support + fixed broken MarkDown LSP support #1101

Open
wants to merge 6 commits into
base: main
Choose a base branch
from

Conversation

alberti42
Copy link

References

Code changes

Changes are documented in the commits.

User-facing changes

No visual changes in the settings.

Backwards-incompatible changes

No changes to API.

Chores

  • linted
  • tested
  • documented
  • changelog entry

I am glad to contribute to all chores if the PR will be considered and the bugs eventually fixed upstream. Before investing more time, I prefer to wait for some reactions from the maintainers. Thanks for your understanding.

Changes are anyhow very limited and small in their extent.

…o have the same in `is_installed_args`. Otherwise, it is erroneously brought to believe that Julia Language Server is not installed.
…ed-language-server` was not found. Now, it is possible to specify multiple locations with `script` were to look for the node script.
… Relative directories such as `.` as was before configured are no longer supported.
Copy link

github-actions bot commented Oct 6, 2024

Binder 👈 Launch a binder notebook on branch alberti42/jupyterlab-lsp/main

@@ -213,17 +213,18 @@ class LanguageServerManagerAPI(LoggingConfigurable, HasListeners):
help=_("additional absolute paths to seek node_modules first"),
).tag(config=True)

def find_node_module(self, *path_frag):
def find_node_module(self, node_module, alternatives):
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this constitutes a breaking change as language specs inheriting from NodeModuleSpec will no longer work. One way to add it in backward compatible way would be to add a new method with new signature and make the old method call the new one.

@krassowski
Copy link
Member

Thank you for the PR, sorry I missed it back in October!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants